<script type="text/javascript" src="js/util.js?v=2022"></script>
<h2>FAQ</h2>

<h3>Where is the encoding option?</h3>
<p>
    This can be set using the JVM's system property 'file.encoding'.
    See the <a href="manual/manual.xml#encoding" target="_blank">manual</a> for more information.
</p>

<h3>Can I save a report in file-system mode?</h3>
<p>
    Yes.
    Please see the <a href="manual/manual.xml#fileSystemSave" target="_blank">manual</a> for more information.
</p>

<h3>How does JSCover maintain quality?</h3>
<p>
    JSCover reuses JSCoverage's regression tests
    (see <a
        href="https://github.com/tntim96/JSCover/blob/master/src/test-integration/java/jscover/instrument/InstrumentAndHighlightRegressionTest.java"
        target="_blank">InstrumentAndHighlightRegressionTest</a>)
    and has added a suite of unit, integration and acceptance tests which give a fairly high degree of coverage (~97%
    line, ~95% branch).
    JavaScript tests have also been added (using Jasmine) and JSCover is used to check JavaScript coverage
    (see <a
        href="https://github.com/tntim96/JSCover/blob/master/src/test-acceptance/java/jscover/server/HtmlUnitJSTest.java"
        target="_blank">HtmlUnitJSTest</a>).
</p>
<p>
    All bugs are corrected by first writing failing test to ensure no regression errors occur.
</p>

<h3>Why won't the coverage report load in Google Chrome or FireFox?</h3>
<h3>Why doesn't the manual load off the file-system in Google Chrome or FireFox?</h3>
<h3>Why don't the web-pages load off the file-system in Google Chrome or FireFox?</h3>
<p>For Chrome: start with '--allow-file-access-from-files' switch</p>
<p>For FireFox</p>
<ol>
    <li>In a new tab, type or paste <b>about:config</b> in the address bar and press Enter/Return. Click the button promising to be careful or accepting the risk.</li>
    <li>In the search box above the list, type or paste <b>uniq</b></li>
    <li>Double-click the <b>privacy.file_unique_origin</b> preference to switch the value from true to <b>false</b></li>
    <li>Firefox > 106 <b>security.fileuri.strict_origin_policy</b> set <b>false</b></li>
</ol>
<p>
    For more information see <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS/Errors/CORSRequestNotHttp" target="_blank">Reason: CORS request not HTTP</a>.<br>
Answer from <a href="https://stackoverflow.com/questions/51081754/cross-origin-request-blocked-when-loading-local-file#answer-57125361" target="_blank">Cross-Origin Request Blocked when loading local file</a>.
</p>

<h3>Does the developer use JSCover on projects</h3>
<p>Yes.</p>

<h3>Does an error log entry mean my coverage report is wrong?</h3>
<p>
    Not necessarily.
    Usually the worst that could happen is that an instrumentation line has been missed.
    See the <a href="manual/manual.xml#logging" target="_blank">manual</a> for more information.
</p>

<h3>JSCoverage FAQ</h3>
<p>Also see the <a href="https://siliconforks.com/jscoverage/faq.html" target="_blank">JSCoverage FAQ</a></p>
